home *** CD-ROM | disk | FTP | other *** search
/ Cream of the Crop 1 / Cream of the Crop 1.iso / VIRUS / VCHK203.ARJ / VIRUSCHK.LJZ < prev    next >
Text File  |  1991-07-16  |  29KB  |  214 lines
  1. &l8c0e66F&aR&l0O
  2.  
  3. (0U(s1p10v0s0b5T*p+255Y*p+95Y(0U(s1p10v0s0b5T                                                                                                    *p1102X(0U(s1p14v0s3b5TViruschk
  4. *p+59Y(0U(s1p14v0s3b5T                                                                         *p1105X(0U(s1p10v0s0b5TVersion 2.03
  5. *p+45Y(0U(s1p10v0s0b5T                                                                                             *p1033X(0U(s1p8v0s0b5TSSgt Jon Freivald, USMC
  6. *p+42Y(0U(s1p8v0s0b5T                                                                                                                          *p1106XTurboC++ 1.0
  7. *p+42Y(0U(s1p8v0s0b5T                                                                                                      Copyright 1991, 1st Marine Corps District
  8. *p+42Y(0U(s1p8v0s0b5T                                                                                                                      *p1068XAll Rights Reserved.
  9. *p+168Y(0U(s1p8v0s0b5T*p240X(0U(s1p14v0s3b5TLICENSING INFORMATION:
  10. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s0b5TViruschk is distributed as freeware.  It may be distributed freely as long as there is no fee charged for it or it's
  11. *p+52Y(0U(s1p10v0s0b5T*p240Xdistribution.  Viruschk must be distributed as a complete package, containing all of the files contained in the file
  12. *p+52Y(0U(s1p10v0s0b5T*p240Xreadme.1st.  Viruschk may not be distributed as a feature with any other software package without the prior
  13. *p+52Y(0U(s1p10v0s0b5T*p240Xwritten permission of 1st Marine Corps District.  There is no fee for registration, however, if you register as a
  14. *p+52Y(0U(s1p10v0s0b5T*p240Xuser, you will be placed on distribution for future updates.  Refer to the notes section for further information on
  15. *p+52Y(0U(s1p10v0s0b5T*p240Xhow to register.
  16. *p+171Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TWHAT IT IS:
  17. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s0b5TThe use of McAfee's Viruscan (scan.exe) on all USMC systems is mandated by CMC/CCI msg R 220032Z
  18. *p+52Y(0U(s1p10v0s0b5T*p240XOCT 90 ZY3.(0U(s1p10v0s3b5T Viruschk(0U(s1p10v0s0b5T is a "shell" or "watchdog" for McAfee's scan.exe. It also displays the warning screen
  19. *p+35Y(0U(s1p10v0s0b5T                                                                                      *p948X(0U(s1p8v0s0b5T1
  20. *p+17Y(0U(s1p8v0s0b5T*p240X(0U(s1p10v0s0b5Tmandated by USMC security regulations *p964X.  If a virus condition is found, it will lock up the user's system and
  21. *p+52Y(0U(s1p10v0s0b5T*p240Xwith a loud tone and unmistakable screen, alert them to the infected condition!  It is highly recommended that
  22. *p+52Y(0U(s1p10v0s0b5T*p240Xyou also use the Vshield program (also by McAfee) - especially if you use the option to limit scanning to once a
  23. *p+52Y(0U(s1p10v0s0b5T*p240Xweek.  Please refer to the referenced message for further guidance regarding use of the McAfee virus
  24. *p+52Y(0U(s1p10v0s0b5T*p240Xprevention software.  This documentation does not cover all policy set forth in the message, nor does it intend
  25. *p+52Y(0U(s1p10v0s0b5T*p240Xto be taken as a statement of policy.
  26. *p+171Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TSYSTEM REQUIREMENTS:
  27. *p+163Y(0U(s1p14v0s3b5T                   *p298X(0U(s1p10v0s0b5To     *p380XIBM PC, PC/XT, PC/AT, PS/2 or 100% compatible computer
  28. *p+104Y(0U(s1p10v0s0b5T                           *p298Xo     *p380X384K RAM
  29. *p+104Y(0U(s1p10v0s0b5T                           *p298Xo     *p380Xa hard disk with one or more DOS partitions
  30. *p+104Y(0U(s1p10v0s0b5T                           *p298Xo     *p380XDOS version 2.0 or higher
  31. *p+104Y(0U(s1p10v0s0b5T                           *p298Xo     *p380XDOS version 3.0 or higher for the integrity self-check
  32. *p+104Y(0U(s1p10v0s0b5T                           *p298Xo     *p380XMcAfee & Associates Viruscan (scan.exe) version 7.2V77 or higher.
  33. *p+133Y(0U(s1p10v0s0b5T*p240X(0U(s1p8v0s0b5T_________________________________________________________________________________________________________________________
  34. (0U(s1p8v0s0b5T                                                                                                                                                                                                                                                 *p2174X_
  35. *p+60Y(0U(s1p8v0s0b5T*p240X1. For non USMC users, you can make this a welcome screen, display a corporate message, etc, or you can eliminate it all together.  The
  36. *p+36Y(0U(s1p8v0s0b5T                              *p273Xcontent of the screen file is irrelevant to the operation of the program.  The file should only be one screen long, or it will scroll before
  37. *p+36Y(0U(s1p8v0s0b5T                              *p273Xthe first part can be read.
  38.  
  39. (0U(s1p8v0s0b5T*p+255Y*p+95Y(0U(s1p8v0s0b5T*p240X(0U(s1p14v0s3b5THOW TO INSTALL IT:
  40. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s0b5TTo install Viruschk, proceed as follows:
  41. *p+104Y(0U(s1p10v0s0b5T*p240XMake a directory on the c: drive named "security" (this is CMC mandated and hard-coded into Viruschk).
  42. *p+104Y(0U(s1p10v0s0b5T*p240XCopy the following files into c:\security:
  43. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5Tviruschk.com
  44. *p+104Y(0U(s1p10v0s3b5T*p240Xscan.exe(0U(s1p10v0s0b5T                               *p727X(This should be the latest version supplied through official channels.  It(0U(s1p10v0s3b5T *MUST*(0U(s1p10v0s0b5T be
  45. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xversion 7.2V77 or higher.)
  46. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5Twarning(0U(s1p10v0s0b5T                               *p727X(This screen may be modified to suit your organization with any ANSI editor such
  47. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xas "TheDraw", or you can substitute it with any ANSI/ASCII screen of your choice,
  48. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xas long as it is named "warning".  If you are not a USMC user, it may be omitted all
  49. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xtogether.)
  50. *p+104Y(0U(s1p10v0s0b5T*p240XAdd the line "c:\security\viruschk" to the beginning of the user's autoexec.bat file.  This line should normally be
  51. *p+35Y(0U(s1p10v0s0b5T                                                                       *p791X(0U(s1p8v0s0b5T2
  52. *p+17Y(0U(s1p8v0s0b5T*p240X(0U(s1p10v0s0b5Tthe first line of the autoexec.bat  *p818X& should ALWAYS be before the user can login to the network.
  53. *p+171Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TWHAT IT DOES:
  54. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s0b5TViruschk first checks the DOS version being run on the machine.  If it is version 3.0 or higher, it performs an
  55. *p+52Y(0U(s1p10v0s0b5T*p240Xintegrity check on itself.  ANY modification (manual tampering, "pklite" compression, a virus, etc) will cause the
  56. *p+52Y(0U(s1p10v0s0b5T*p240Xvirus warning screen to display and the system to lock up.  If the DOS is less than version 3.0, a message is
  57. *p+52Y(0U(s1p10v0s0b5T*p240Xdisplayed stating that the self-check cannot be performed.
  58. *p+104Y(0U(s1p10v0s0b5T*p240XIt then checks the command line.  The following command line options are valid:
  59. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5Tdisplay(0U(s1p10v0s0b5T                                *p727Xshows the "lockup" screen & plays a snippet of the warning tones - no scan is
  60. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xperformed and the warning screen is not displayed (this is included for demo
  61. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xpurposes only!)
  62. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TMon(0U(s1p10v0s0b5T                                    *p727XExecutes scan.exe on Monday only
  63. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TTue(0U(s1p10v0s0b5T                                      *p727XExecutes scan.exe on Tuesday only
  64. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TWed(0U(s1p10v0s0b5T                                     *p727XExecutes scan.exe on Wednesday only
  65. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TThu(0U(s1p10v0s0b5T                                     *p727XExecutes scan.exe on Thursday only
  66. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TFri(0U(s1p10v0s0b5T                                       *p727XExecutes scan.exe on Friday only
  67. *p+65Y(0U(s1p10v0s0b5T*p240X(0U(s1p8v0s0b5T_________________________________________________________________________________________________________________________
  68. (0U(s1p8v0s0b5T                                                                                                                                                                                                                                                 *p2174X_
  69. *p+60Y(0U(s1p8v0s0b5T*p240X2. If you use Zenith DOS with manual partition assignment, make sure that you place the asgnpart command BEFORE Viruschk or the
  70. *p+36Y(0U(s1p8v0s0b5T                              *p273Xadditional partitions will not get scanned!
  71. *p+72Y(0U(s1p8v0s0b5T                              *p273XIf your system does not have an internal clock/calendar, the DOS date command should be in the autoexec.bat prior to the viruschk
  72. *p+36Y(0U(s1p8v0s0b5T                              *p273Xline.
  73. *p+172Y(0U(s1p8v0s0b5T                                                                                                                                   *p1180X(0U(s1p10v0s0b5T- 2 -
  74.  
  75. (0U(s1p10v0s0b5T*p+255Y*p+80Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TSat(0U(s1p10v0s0b5T                                      *p727X* Executes scan.exe on Saturday only
  76. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5TSun(0U(s1p10v0s0b5T                                     *p727X* Executes scan.exe on Sunday only
  77. *p+104Y(0U(s1p10v0s0b5T                                                                  *p727X* = NOT ALLOWED ON USMC SYSTEMS - these options are only included for
  78. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xthose who wish to use this program on their private systems.
  79. *p+104Y(0U(s1p10v0s0b5T*p240XIf no command line (or one not listed above) argument is given, scan.exe will be executed every day.  The
  80. *p+52Y(0U(s1p10v0s0b5T*p240Xcommand line arguments MUST be typed exactly as they are above (i.e., "mon" is not equivalent to "Mon").
  81. *p+104Y(0U(s1p10v0s0b5T*p240XIf scan.exe is to be executed, Viruschk will then build a table of all valid hard drives for the system.  It will then
  82. *p+52Y(0U(s1p10v0s0b5T*p240Xexecute scan.exe with the proper parameters to scan all the drives.  If scan.exe is not to be executed that day,
  83. *p+52Y(0U(s1p10v0s0b5T*p240Xthis step will be skipped.
  84. *p+104Y(0U(s1p10v0s0b5T*p240XIf scan.exe is to be executed, and this is the first time for this particular day, scan will be executed with the
  85. *p+52Y(0U(s1p10v0s0b5T*p240X"/NOBREAK" parameter - this will force a complete scan at least once each (selected) day.  If this is a
  86. *p+52Y(0U(s1p10v0s0b5T*p240Xsubsequent run, the "/NOBREAK" parameter will be omitted, allowing the user to press <Ctrl><C> or
  87. *p+52Y(0U(s1p10v0s0b5T*p240X<Ctrl><Break> to bypass the scanning process.  The first run force is controlled by a control file.  This is a 4
  88. *p+52Y(0U(s1p10v0s0b5T*p240Xbyte file named "c:\security\viruschk.lrd".  This file will be created the first time the program is run and will be
  89. *p+52Y(0U(s1p10v0s0b5T*p240Xre-created automatically if it is deleted.
  90. *p+104Y(0U(s1p10v0s0b5T*p240XThe control file is updated to reflect the current date AFTER the forced scan.  If the system is rebooted during
  91. *p+52Y(0U(s1p10v0s0b5T*p240Xthe scan, the scan will again be forced.  This will continue until the scan completes and the control file is
  92. *p+52Y(0U(s1p10v0s0b5T*p240Xupdated.
  93. *p+104Y(0U(s1p10v0s0b5T*p240XViruschk will then display the file "warning" for a period of 30 seconds if it exists.  You will only get this far if
  94. *p+52Y(0U(s1p10v0s0b5T*p240Xone of the following two conditions are met:
  95. *p+104Y(0U(s1p10v0s0b5T                                    *p400X1.  scan.exe is not to be run that day
  96. *p+52Y(0U(s1p10v0s0b5T                                    *p400X2.  scan.exe ran successfully and did not find any viruses
  97. *p+104Y(0U(s1p10v0s0b5T*p240XAfter the 30 second delay, control will release back to DOS and the user's system can continue running it's
  98. *p+52Y(0U(s1p10v0s0b5T*p240Xautoexec.bat file.  The user can bypass the delay by pressing a key.  A countdown timer informs you of how
  99. *p+52Y(0U(s1p10v0s0b5T*p240Xmuch longer you have to wait if you don't press a key.  The warning screen will display every day, regardless of
  100. *p+52Y(0U(s1p10v0s0b5T*p240Xcommand line arguments (except "display" which is not for general use anyway...).  If the file
  101. *p+52Y(0U(s1p10v0s0b5T*p240Xc:\security\warning does not exist, nothing will be displayed, and there will be no delay before the program
  102. *p+52Y(0U(s1p10v0s0b5T*p240Xexits.
  103. *p+255Y*p+255Y*p+255Y*p+188Y(0U(s1p10v0s0b5T                                                                                                           *p1180X- 3 -
  104.  
  105. (0U(s1p10v0s0b5T*p+255Y*p+95Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TWHAT WILL TRIGGER IT:
  106. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s0b5TOne of five conditions will cause viruschk to lock up the user's
  107. *p+52Y(0U(s1p10v0s0b5T*p240Xsystem:
  108. *p+104Y(0U(s1p10v0s0b5T                                    *p400X1. Viruschk.exe finds any type of modification has occurred to itself (indicating either manual
  109. *p+52Y(0U(s1p10v0s0b5T*p240Xtampering or a virus).
  110. *p+52Y(0U(s1p10v0s0b5T                                    *p400X2. Scan.exe was not in the c:\security directory or could not be executed.
  111. *p+52Y(0U(s1p10v0s0b5T                                    *p400X3. Scan.exe found viruses present on the system.
  112. *p+52Y(0U(s1p10v0s0b5T                                    *p400X4. Scan.exe exited with an error code.
  113. *p+52Y(0U(s1p10v0s0b5T                                    *p400X5. Your version of scan.exe is not at least 7.2V77.
  114. *p+104Y(0U(s1p10v0s0b5T*p240XGiven any of the 5 conditions, we do not want the user to be able to proceed and use his system (possibly
  115. *p+52Y(0U(s1p10v0s0b5T*p240Xspreading a virus..!), so viruschk sounds a warning tone on the PC's speaker & displays a screen leaving the user
  116. *p+52Y(0U(s1p10v0s0b5T*p240Xno doubt about the fact that a virus has been encountered (even though that is but one of five possible exit
  117. *p+52Y(0U(s1p10v0s0b5T*p240Xcodes).  The user's system will now be locked - the only keystrokes that will have any effect is
  118. *p+52Y(0U(s1p10v0s0b5T*p240X<Ctrl><Alt><Del> and (if you have a Zenith system) <Ctrl><Alt><Ins> (so that you can boot  from a
  119. *p+52Y(0U(s1p10v0s0b5T*p240Xwrite protected floppy disk and remedy the problem).
  120. *p+104Y(0U(s1p10v0s0b5T*p240XFor a demo of the warning screen type:
  121. *p+104Y(0U(s1p10v0s0b5T                                    *p400Xviruschk display
  122. *p+104Y(0U(s1p10v0s0b5T*p240Xwhen display is on the command line, scan will not be executed, nor will warning be displayed - this is for admin
  123. *p+52Y(0U(s1p10v0s0b5T*p240Xdemo use only.
  124. *p+255Y*p+255Y*p+255Y*p+255Y*p+255Y*p+228Y(0U(s1p10v0s0b5T                                                                                                           *p1180X- 4 -
  125.  
  126. (0U(s1p10v0s0b5T*p+255Y*p+95Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TRETURN CODES:
  127. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s0b5TViruschk will set the DOS errorlevel upon exit.  You can use the DOS batch command "if errorlevel" to check
  128. *p+52Y(0U(s1p10v0s0b5T*p240Xthese codes and take conditional action if desired.  The following is a list of the codes & their significance:
  129. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T0(0U(s1p10v0s0b5T                                          *p727XViruschk ran uninterrupted to completion of the delay countdown or the "display"
  130. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xcommand line option was used.
  131. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T1(0U(s1p10v0s0b5T                                          *p727XA keystroke was pressed to bypass the delay.
  132. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2(0U(s1p10v0s0b5T                                          *p727XThe file c:\security\warning was not found (therefore no display or delay).
  133. *p+87Y(0U(s1p10v0s0b5T                                                                                                                                                                    *p1813X(0U(s1p8v0s0b5T3
  134. *p+17Y(0U(s1p8v0s0b5T*p240X(0U(s1p10v0s3b5T3(0U(s1p10v0s0b5T                                          *p727XWarning was present, but the program was unable to display it *p1829X.
  135. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T100(0U(s1p10v0s0b5T                                      *p727XYou errantly obtained a copy of the program that does not have the anti-virus
  136. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xinformation imbedded in it.  This copy should not have been distributed and will not
  137. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xrun with DOS 3.0 or higher.
  138. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T255(0U(s1p10v0s0b5T                                      *p727XThe DOS version being run is less than version 2.0.  Viruschk requires at least
  139. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xversion 2.0 to run and at least 3.0 to perform it's self-check.
  140. *p+171Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TCOMMON PROBLEMS/REMEDIES:
  141. *p+163Y(0U(s1p14v0s3b5T                   *p290X(0U(s1p10v0s0b5T1.     *p380XScan.exe cannot execute - Viruschk locks up system - scan.exe will execute when invoked manually.
  142. *p+104Y(0U(s1p10v0s0b5T                                       *p430Xa.     *p520XMemory - scan.exe requires 256K of RAM.  Adding the overhead of Viruschk brings system
  143. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xrequirements up to 384K. It doesn't actually require that much, but that is the next step up from
  144. *p+52Y(0U(s1p10v0s0b5T                                               *p520X256K.
  145. *p+104Y(0U(s1p10v0s0b5T                                      *p428Xb.     *p520XLocation - scan.exe MUST be located in C:\SECURITY. Because this location was mandated
  146. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xby CMC, it has been hard-coded into Viruschk.  If it cannot execute the program
  147. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xc:\security\scan.exe, it is considered an error & the lock up is initiated on purpose.  This
  148. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xprevents a virus from planting a trojan "scan" elsewhere in your path and having it executed by
  149. *p+52Y(0U(s1p10v0s0b5T                                               *p520XViruschk.
  150. *p+104Y(0U(s1p10v0s0b5T                                       *p432Xc.     *p520XVersion - starting with Viruschk version 2.01c, Viruscan (scan.exe) 7.2V77 is the minimum
  151. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xversion required.
  152. *p+104Y(0U(s1p10v0s0b5T                          *p290X2.     *p380XMy warning screen comes out looking like a bunch of jumbled garbage.
  153. *p+104Y(0U(s1p10v0s0b5T                                       *p430Xa.     *p520XMost likely your screen was done in ANSI graphics and you do not have ansi.sys loaded.  Insure
  154. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xthat your config.sys file contains a line something to the effect of "device=c:\dos\ansi.sys".  If it
  155. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xdoes not, add the line (make sure you give the correct path to ansi.sys), then reboot your
  156. *p+52Y(0U(s1p10v0s0b5T                                               *p520Xsystem.
  157. *p+157Y(0U(s1p10v0s0b5T*p240X(0U(s1p8v0s0b5T_________________________________________________________________________________________________________________________
  158. (0U(s1p8v0s0b5T                                                                                                                                                                                                                                                 *p2174X_
  159. *p+60Y(0U(s1p8v0s0b5T*p240X3. This condition should **p607XN*p634XE*p659XV*p686XE*p711XR*p738X* *p765Xhappen!  If it does, please contact me because I'm interested in knowing if this can actually happen.
  160. (0U(s1p8v0s0b5T                                                                 *p591X**p609XN*p636XE*p661XV*p688XE*p713XR*p740X*
  161. *p+172Y(0U(s1p8v0s0b5T                                                                                                                                   *p1180X(0U(s1p10v0s0b5T- 5 -
  162.  
  163. (0U(s1p10v0s0b5T*p+255Y*p+95Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TNOTES:
  164. *p+163Y(0U(s1p14v0s3b5T                          *p400X(0U(s1p10v0s0b5TThe author can be contacted to register or for support in the following ways:
  165. *p+104Y(0U(s1p10v0s0b5T*p240XCommanding Officer
  166. *p+52Y(0U(s1p10v0s0b5T*p240XHeadquarters, 1st Marine Corps District (ISMO)
  167. *p+52Y(0U(s1p10v0s0b5T*p240X605 Stewart Avenue
  168. *p+52Y(0U(s1p10v0s0b5T*p240XGarden City, NY 11530
  169. *p+52Y(0U(s1p10v0s0b5T                                    *p400XATTN: SSgt Freivald
  170. *p+104Y(0U(s1p10v0s0b5T*p240XCommercial phone - (516) 228-5635
  171. *p+52Y(0U(s1p10v0s0b5T*p240XAutovon phone - 994-5635
  172. *p+52Y(0U(s1p10v0s0b5T*p240XELMS/MCDN - bk1md4:gisnad05
  173. *p+52Y(0U(s1p10v0s0b5T*p240XCompuserve - 70274,666
  174. *p+52Y(0U(s1p10v0s0b5T*p240XInternet - 70274.666@compuserve.com
  175. *p+52Y(0U(s1p10v0s0b5T*p240XProdigy - ktfp55a
  176. *p+52Y(0U(s1p10v0s0b5T*p240XBBS - (516) 483-5841 (8,N,1 - 300-2400,9600 HST)
  177. *p+104Y(0U(s1p10v0s0b5T                                    *p400XI wrote this program to take care of two CMC mandates for the users of our network as transparently
  178. *p+52Y(0U(s1p10v0s0b5T*p240Xas possible.  It has also been implemented on all of our remote/stand-alone systems.  Those mandates are the
  179. *p+52Y(0U(s1p10v0s0b5T*p240Xaccess warning screen on system startup and the scanning of all hard drives at least once a week.
  180. *p+104Y(0U(s1p10v0s0b5T                                    *p400XPlease contact me ASAP if you have any problems with this program.  We have tested it on over 90
  181. *p+52Y(0U(s1p10v0s0b5T*p240Xsystems here at 1st District, but our configurations are pretty standard, so I can't GUARANTEE that it will run
  182. *p+52Y(0U(s1p10v0s0b5T*p240Xproperly on ALL systems (although I believe it will).
  183. *p+104Y(0U(s1p10v0s0b5T                                    *p400XI am also open to comments and suggestions for improvements.  Having reached this stage, updates
  184. *p+52Y(0U(s1p10v0s0b5T*p240Xare not very high on the priority list, but I will definitely entertain them.  I may also be willing to produce
  185. *p+52Y(0U(s1p10v0s0b5T*p240Xcustom versions for specific requirements.  This will depend on what they are (the amount of work involved),
  186. *p+52Y(0U(s1p10v0s0b5T*p240Xrequested delivery deadlines, and my current workload here at 1st District.
  187. *p+104Y(0U(s1p10v0s0b5T                                    *p400XIf you would like to be placed on distribution for any future updates, simply drop me a message (either
  188. *p+52Y(0U(s1p10v0s0b5T*p240XUS Mail or Electronic Mail) with your name, unit, address (E-Mail!?), etc...  Be sure to mention Viruschk, as I
  189. *p+52Y(0U(s1p10v0s0b5T*p240Xmaintain distribution lists for a number of programs & want to be sure to get you on the right list..!  Also,
  190. *p+52Y(0U(s1p10v0s0b5T*p240Xplease mention the version that you currently have.
  191. *p+255Y*p+255Y*p+255Y*p+218Y(0U(s1p10v0s0b5T                                                                                                           *p1180X- 6 -
  192.  
  193. (0U(s1p10v0s0b5T*p+255Y*p+95Y(0U(s1p10v0s0b5T*p240X(0U(s1p14v0s3b5TREVISION HISTORY:
  194. *p+163Y(0U(s1p14v0s3b5T                (0U(s1p10v0s3b5T2.03(0U(s1p10v0s0b5T                                     *p727XFixed a bug that would cause a divide error with program termination if a RAM
  195. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727XDrive or hard disk partition was smaller than one meg or had less than one meg
  196. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xfree.
  197. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2.02(0U(s1p10v0s0b5T                                     *p727XAdded the feature of "/NOBREAK" being passed to scan.exe only on the first run
  198. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xof any given day.  This added the requirement for a 4 byte control file, which is
  199. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xnamed "c:\security\viruschk.lrd" (lrd stands for "last run date").
  200. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2.01c(0U(s1p10v0s0b5T                                    *p727XUpdated the code to invoke scan.exe with the "/M", "/NOPAUSE" and
  201. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727X"/NOBREAK" options.  This update requires the use of Viruscan (scan.exe) version
  202. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727X7.2V77 or higher.
  203. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2.01b(0U(s1p10v0s0b5T                                   *p727XAdded (actually just made consistent & documented) DOS errorlevel exits.
  204. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2.01a(0U(s1p10v0s0b5T                                    Captured the keystroke if the delay was bypassed to prevent inadvertent input to the
  205. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xnext program run.
  206. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2.01(0U(s1p10v0s0b5T                                     *p727XAdded drive information display, changed 5 second delay to a 30 second delay
  207. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xbypassable with a keystroke, and made the warning screen optional.
  208. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T2.0(0U(s1p10v0s0b5T                                       *p727XAdded integrity (virus) self-check, system interrogation for drive table and option to
  209. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xrun on a specific day of the week.  Converted from .exe to .com format.
  210. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727XDocumentation written.  First general distribution.
  211. *p+104Y(0U(s1p10v0s0b5T*p240X(0U(s1p10v0s3b5T1.0(0U(s1p10v0s0b5T                                       *p727XFirst release, not distributed beyond First District users.  Would only scan drive c:,
  212. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xhad a fixed 5 second delay for the warning screen (which was required), and ran
  213. *p+52Y(0U(s1p10v0s0b5T                                                                  *p727Xevery day.
  214. *p+255Y*p+255Y*p+255Y*p+255Y*p+255Y*p+20Y(0U(s1p10v0s0b5T                                                                                                           *p1180X- 7 -